Audit and Debug Logging

The audit and debug logging facility allows you to maintain a record of activity through an App Server by storing various messages, including error messages, which provide information about what's been happening.

Some of these messages are stored in the App Server Configuration Database, some in the Windows Event Log and others to file.

 

App Server automatically writes various service level events, such as starting and stopping, IP Port status (i.e. listen status of the server's IP port), database connectivity status, licence errors and other service-level errors, to the Windows Event Log. These messages are written to the NDL Digitise App Server log in the Application and Services Logs folder and can be viewed using the Windows Event Viewer. Logging of these messages is not affected by the configuration options available in App Manager (described below). If you experience problems when using Digitise Apps or running your Digitise apps, we suggest you check this log for any messages relating to the issue.

 

The remainder of this topic refers to log messages written to the App Server Configuration Database and to file. Logging stored in the App Server Configuration Database is also referred to in this help as the standard audit log.

 

App Manager allows you to turn the standard audit logging on and off and to specify a logging level, which determines which messages are written to the log. This configuration can be done at the system level or on an individual app or user basis (see below).

There are two different levels of logging – Audit and Debug.

Audit logging is the default level which stores general information about what has been happening at the server side, e.g. incoming connections, user logons, data downloads, error messages etc., to the standard audit log.

Debug logging adds extra server-side messages to the standard audit log, which record more technical information to help in the event that you experience problems using Digitise Apps. In addition, debug logging records the dialog between your App Server and Digitise Apps Client devices to file. You should only use the Debug level if you are experiencing problems, since this level stores significantly more information than the default audit level.

 

Audit and debug server-side messages are stored in the App Server Configuration Database.

The Client-Server communications debug messages are also logged server-side but are saved to file rather than in the App Server Configuration Database. A new log file will be produced each day, as long as the Audit Level is set to Debug, called:

Transaction_<date>.log

where <date> is in the format DD_MM_YYYY. These files are stored in the following folder:

C:\Users\All Users\ndl Software\Digitise Apps\Logging

You can read the entries in these log files using a standard text editor, such as Notepad or Notepad++.

  • Messages longer than 2065 bytes are truncated within the audit log. If you need to know the contents of larger messages, then you can use the log to file facility which doesn't truncate the messages.

 

By default, audit-level logging is turned on for the server, meaning that all apps and users will perform this level of logging. You can change this within App Manager, using the logging settings available on the Properties tabs under the Server, Application and User categories.

You can also use App Manager to read the standard audit log, using the Audit tabs under the same App Manager categories and also under the Device category.